Skip to content

chore(master): release synapse-core 0.2.0 #482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
github-actions wants to merge 1 commit into
base: master
Choose a base branch
from
Open

chore(master): release synapse-core 0.2.0 #482

github-actions wants to merge 1 commit into from
+41 −2

Conversation

@github-actions
Copy link
Contributor

@github-actions github-actions bot commented Dec 4, 2025 •
edited
Loading

📦 Release Preparation

0.2.0 (2026-01-20)

⚠ BREAKING CHANGES

  • replace getMaxProvingPeriod() and getChallengeWindow() with getPDPConfig() (#526)
  • use activePieceCount for accurate piece tracking (#517)

refactor

  • replace getMaxProvingPeriod() and getChallengeWindow() with getPDPConfig() (#526) (a4956c7)

Features

Bug Fixes

  • treat status code 202 for findPiece as a retry (6b9e03f)

Chores

🚀 How to Release

  1. Review the changelog and version bump in this PR
  2. Merge this PR to trigger the release
  3. After merging, the workflow will:
    • Create a GitHub release with tag ${version}
    • Publish to npm automatically
  4. Wait until the workflow is complete before merging another release PR

⚠️ Note: The release has NOT been created yet. It will only be created after you merge this PR.

@github-project-automation github-project-automation bot moved this to 📌 Triage in FOC Dec 4, 2025
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Dec 4, 2025 •
edited
Loading

Deploying with  Cloudflare Workers  Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status Name Latest Commit Preview URL Updated (UTC)
⛔ Deployment terminated
View logs		 synapse-dev 6cc1103 Commit Preview URL

Branch Preview URL		 Jan 21 2026, 12:10 AM

@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 7 times, most recently from fd036e2 to bedf405 Compare December 11, 2025 12:34
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 2 times, most recently from 1fd14fd to 6f48b87 Compare December 15, 2025 12:27
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch from b04c91a to e506c4f Compare December 16, 2025 15:05
@BigLep BigLep moved this from 📌 Triage to 🐱 Todo in FOC Dec 17, 2025
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 3 times, most recently from 7bd8a8c to 3a6cbdf Compare December 18, 2025 17:37
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch from 3a6cbdf to 57b1d6a Compare January 5, 2026 01:11
@socket-security
Copy link

socket-security bot commented Jan 5, 2026 •
edited
Loading

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ? → npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm entities is 91.0% likely obfuscated

Confidence: 0.91

Location: Package overview

From: ? → npm/[email protected]

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at [email protected].

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/[email protected]. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@github-actions github-actions bot changed the title chore(master): release synapse-core 0.1.5 chore(master): release synapse-core 0.2.0 Jan 5, 2026
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 7 times, most recently from 1d21e0a to dd1b179 Compare January 8, 2026 09:34
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 2 times, most recently from c5285fc to 1c2b99a Compare January 12, 2026 03:59
@socket-security
Copy link

socket-security bot commented Jan 12, 2026 •
edited
Loading

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security		 Vulnerability Quality Maintenance License
Added@​hugomrdias/​docs@​0.1.117710010092100
Addedexpressive-code-twoslash@​0.5.3801007883100
Addedastro-mermaid@​1.3.19410010086100
Addedastro@​5.16.11971008898100

View full report

@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 2 times, most recently from 237250b to e0af9c5 Compare January 15, 2026 01:52
@BigLep BigLep added this to the M4: Filecoin Service Liftoff milestone Jan 15, 2026
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch 5 times, most recently from 9250f21 to 521df4d Compare January 20, 2026 11:49
@github-actions github-actions bot force-pushed the release-please--branches--master--components--synapse-core branch from 521df4d to 6cc1103 Compare January 20, 2026 23:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@hugomrdias hugomrdias Awaiting requested review from hugomrdias hugomrdias is a code owner

@rvagg rvagg Awaiting requested review from rvagg rvagg is a code owner

Assignees

No one assigned

Labels

autorelease: pending

Projects

FOC
Status: 🐱 Todo

Milestone

M4: Filecoin Service Liftoff

Development

Successfully merging this pull request may close these issues.

Add type validation to docs

2 participants

@BigLep